Declassifying of suspicious messages

ABSTRACT

Handling a message comprises: classifying an incoming message for a recipient, storing the classified message and providing a notification to the recipient, wherein the notification includes summary information about the classified message and an interface that allows the recipient to operate on the classified message.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to electronic messages. Morespecifically, handling messages with selective user participation isdisclosed.

2. Description of the Related Art

Electronic messages have become an indispensable part of moderncommunication. Electronic messages such as email or instant messages arepopular because they are fast, easy, and have essentially no incrementalcost. Unfortunately, these advantages of electronic messages are alsoexploited by marketers who regularly send out unsolicited junk messages.The junk messages are referred to as “spam”, and spam senders arereferred to as “spammers”. Spam messages are a nuisance to users. Theyclog email inboxes, waste system resources, often promote distastefulsubjects, and sometimes sponsor outright scams.

Although there are many existing message classification systems capableof classifying spam messages, the current message classification systemstypically cannot perfectly classify every message. Sometimes alegitimate email message may be erroneously classified as spam. Thesetypes of misidentifications are sometimes referred to as “falsepositives”. A variety of factors may lead to false positives. Forexample, a message may include certain keywords that would cause thespam filtering system to identify the message as spam, even though thesewords were used in a legitimate context. Although more sophisticatedspam identification algorithms may reduce the rate of false positives,whether a message is spam is ultimately judged by the human recipient.However, requiring the user to make a classification for every messageis impractical, and defeats the purpose of having a spam filteringsystem. It would be desirable to have a message handling system thatcould ameliorate the problem of false positive identifications withoutrequiring significant effort by its users.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating a message handling systemaccording to some embodiments.

FIG. 2 is a flowchart illustrating the operations of an embodiment of amessage filter.

FIG. 3A is a diagram illustrating a notification according to someembodiments.

FIG. 3B is a flowchart illustrating the generation of notificationsaccording to some embodiments.

FIG. 4 is a flowchart illustrating the processing of an incoming messageaccording to some embodiments of the message filter.

FIG. 5 is a flowchart illustrating the handling of a mailing listmessage according to some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess, an apparatus, a system, a composition of matter, a computerreadable medium such as a computer readable storage medium or a computernetwork wherein program instructions are sent over optical or electroniccommunication links. In this specification, these implementations, orany other form that the invention may take, may be referred to astechniques. In general, the order of the steps of disclosed processesmay be altered within the scope of the invention.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

Handling messages with selective user participation is disclosed. Insome embodiments, incoming messages are classified and stored ifappropriate. Certain of the messages may at least preliminarily beclassified as junk. Some or all of the junk messages may be selected fornotification to the user and possible evaluation by the user. Anotification that includes summary information about selected classifiedmessages and an interface that allows the recipient to operate on theclassified messages is provided to the recipient. For the purposes ofexample, handling of email messages in computer networks is discussedextensively throughout this specification. The approach is alsoapplicable to instant messages, text or picture messages transmitted viapersonal digital assistants (PDAs), cellular phones, or any otherappropriate applications and devices.

FIG. 1 is a block diagram illustrating a message handling systemaccording to some embodiments. In this example, incoming messages areclassified by message filter 100. A database 102 (also referred to as ajunk store) is associated with the message filter and is used to storecertain classified messages. The database may be located on the samedevice as the message filter, or on a separate device or network (forexample, the database may be a part of a data center). Message filter100 forwards messages and notifications to message servers such as 104and 108. Examples of such message servers include Microsoft ExchangeServer, Lotus Notes Server, SendMail server, etc. The message serversdistribute the messages and notifications to message clients (such as106 and 110) that send and receive messages and provide an interface fora user to interact with the messages and notifications.

FIG. 2 is a flowchart illustrating the operations of an embodiment of amessage filter. In this example, incoming messages are classified by themessage filter (200). The message filter may employ a variety ofclassification techniques, such as whitelisting, thumbprinting,statistical analysis, or any other appropriate methods. The classifiedmessages are stored if appropriate (202). Messages may be classified asgood, non-spam messages or suspicious messages that are potentiallyjunk. The suspicious messages are blocked by the message filter and notdelivered to the recipients immediately. The suspicious messages aretemporarily stored (or “quarantined”) in a database/junk storeassociated with the message filter, such as database 102 of FIG. 1. Insome embodiments, the quarantined messages are stored on a per-recipientbasis in the database. At a prescribed time, notifications about theclassified messages are provided to the recipients (204). In someembodiments, a notification to a recipient includes information aboutthe latest quarantined messages (i.e. messages that have beenquarantined since the last notification was sent) for this recipient,and an interface that allows the recipient to operate on the message.Details of the notification are described below.

FIG. 3A is a diagram illustrating a notification according to someembodiments. In this example, the notification is generated periodicallyand sent to the recipient/user at a scheduled time as an email messagein HTML format. The content of notification 300 is displayed in themessage client as a regular email. Included in the notification is areport 302 that provides the recipient with more details about thequarantined messages, such as the recipient address, number of messagesplaced in the junk box, instructions for retrieving any of the messages,the number of days until the quarantined messages are deleted if noaction is taken, etc.

Also included in the notification is a summary of the quarantinedmessages. In this example, summary 304 displays the sender address andthe subject of each quarantined message as well as the reason forquarantining the message. Examples of the reason include that themessage is from a sender on the block list, the message is determined tobe a virus, other users have classified the message as junk, etc. Aninterface (such as interface 306) is provided with each message to allowthe recipient to operate on the message. In the example shown, theinterface includes an “unjunk” link and a “view” link. In someembodiments, if “unjunk” is selected, the message is delivered to therecipient's inbox as a regular email message. The message in thedatabase may be deleted, or marked as having been delivered. In someembodiments, the sender address is also added to the recipient's allowedlist. In some embodiments, a popup dialog window opens to tell therecipient about the status of the email. Some of the possibilitiesinclude that the message has been delivered, that the message'squarantine period has expired, or that the message has been junked andcannot be junked again. In this example, the recipient's allowed list ismanaged by the message filter. Messages from addresses in the allowedlist are automatically treated as good messages and are not blocked.

The “view” link is associated with a universal resource locator (URL)through which the message can be displayed. If “view” is selected, themessage is shown to the user as a web page, in a safe environment on aserver. If the recipient does not take any action with respect to amessage, the message will be deleted from the database after itsquarantine period expires. In some embodiments, the user isauthenticated before he is allowed to unjunk or view messages.

Also included in the notification are settings 308 that allow the userto change various configuration options. In this example, the settingsare shown as links to configuration and management pages. The settingsinclude anti-spam settings that allow the recipient to change theaddresses in the allowed/blocked list as well as how aggressive the spamclassification rules should be set. The settings also include managementsettings, including what actions to take with junk messages (forexample, the user may choose to delete the junk messages permanently, orsave them to a designated folder), the frequency at which thenotifications are sent, etc. The user may also delegate control toothers. In other words, the user may designate another user as adelegate who can review notifications sent to the user. Any messageunjunked by the delegate will be delivered to the inbox of the originalintended recipient (i.e. the user). In some embodiments, the user isallowed to choose the sender email address of the notification messageso that the client application can apply rules to better manage thenotification messages (for example, all notifications may be configuredto originate from a special email address so that they may be stored ina particular folder.)

In some embodiments, the settings may also allow the user to view spamreports and download additional anti-spam applications or upgrades. Spamreports may include information about how many messages have beenfiltered, along with reasons why, messages or other data of interest. Inaddition to managing the settings via the links provided by thenotification message, the user may also change the settings by logginginto a website associated with the message filter.

The notification may be generated using a template that includesvariables for information specific to the recipient or the notification.In one example, the following template is used to generate the junknotification shown in FIG. 3A:

TABLE-US-00001 TABLE US-00001 <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML4.01 Transitional//EN”><html><head><title>MailFrontier JunkNotification</title><meta http-equiv=“Content-Type” content =“text/html;charset=iso-88591”> </head><body><b><font size=“2”face=“verdana, Arial,Helvetica, sans-serif”>Junk Box Summary for:%RECIPIENT%</FONT></B><BR>The %NUMEMAILS% %EMAIL_OR_EMAILS% listed below%HAS_OR_HAVE% been placed in your personal Junk Box<br>since your lastJunk Box Summary and will be deleted after %NUM_DAYS%%DAY_OR_DAYS%<br><br>To receive any of these messages, click UnJunk. Themessage will be delivered to your inbox and the sender will be added toyour Allowed List so their emails are neverblocked.</font><br><br><b>Junk Box Summary</b><br><font size=“1”face=“monospace,Courier”>------------<br>%JUNK_SUMMARIES%------------------------------------</font><b-r><fontsize=“2” face=“verdana, Arial, Helvetica, sans-serif”>To manage yourpersonal junk email blocking settings, log in using<br>your standardusername/password combination: <br><ahref=“%ASG_LOGIN_URL%”>%ASG_LOGIN_URL%</a><br><br>Ju-nk blocking byMailFrontier, Inc.<br></font></body></html>

In the template, each variable is delimited using two “%” signs at thebeginning and the end of the variable names, although any other suitablesymbols may also be used. Examples of such variables include RECIPIENT(for displaying the address or user name of the recipient), NUMEMAILS(for displaying the message count of quarantined messages listed in thenotification), NUM_DAYS (for displaying the number of quarantine daysuntil the messages are deleted), JUNK_SUMMARIES (for displaying theinformation about the quarantined messages), ASG_LOGIN_URL (fordisplaying the URL associated with the website where the user may loginand manage his quarantined messages), etc.

FIG. 3B is a flowchart illustrating the generation of notificationsaccording to some embodiments. In this example, the notifications aregenerated periodically according to a schedule. At a scheduled time(550), a script is launched (552). According to the script, eachquarantined message in the database is examined. If a next email messageis available (554), its status is checked (556). If the message is to bedeleted because its quarantine period has expired, or if it has beenmarked as delivered because the user has unjunked it, the message isremoved from the database (560). If the message has not yet beenincluded in a notification, it is added to the list for notification(558). In some embodiments, summary information for the message, such assender address (i.e. “From” address) and subject are added to a listindexed according to the recipient addresses. The status check isperformed for all the available email in the database. When all themessages are processed, notifications to the recipients are sent (562).The process then waits until the next scheduled time (550), when theprocedure is repeated.

A strategy sometimes used by spammers to reach the maximum number ofaudience is to flood a domain with many combinations of possible usernames. As a result, a large number of spam messages with non-existentuser addresses may reach the message filter. In some embodiments, themessage filter can reduce the number of messages to be quarantined byverifying the recipient address of the message. FIG. 4 is a flowchartillustrating the processing of an incoming message according to someembodiments of the message filter. In this example, once an incomingmessage is received (400), it is determined whether the recipient'saddress corresponds to a real address (402). In some embodiments, themessage filter cooperates with the message servers, directory servers orany appropriate devices/applications that can provide user accountinformation. For example, the message filter may send a query based onthe recipient's address to a lightweight directory access protocol(LDAP) server to determine whether the address exists in the system. Ifthe recipient address does not correspond to a real address in thesystem, the message is discarded (404). If, however, the recipientaddress corresponds to a real address, it is classified as usual anddetermined whether it is potentially junk (406). If the message is notjunk, it is delivered to the recipient (408). Otherwise, the message isquarantined (410).

Sometimes a user may subscribe to a distribution list (such as a mailinglist) and subsequently receive messages addressed to the distributionlist. For example, a user whose address is userA@mailfrontier.com maysubscribe to mailing lists such as engineering@mailfrontier.com andsales@mailfrontier.com. In some embodiments, the recipient receivesdifferent notifications for the mailing list messages and the messagesdirectly addressed to him. In other words, userA would receive threeseparate notifications for quarantined message addressed to userA,engineering and sales. In some embodiments, for the same recipient, thenotification of quarantined messages addressed to the mailing lists andthe notification of quarantined messages addressed directly to therecipient are coalesced to reduce the number of notifications one mayreceive. In such embodiments, userA would receive a single notificationthat includes information about quarantined messages addressed to userAas well as to engineering and sales mailing list. In some embodiments,the message client has additional capabilities that can identifynotifications from multiple sources and combine them into a singlenotification.

The handling of mailing list messages may vary depending onimplementation. FIG. 5 is a flowchart illustrating the handling of amailing list message according to some embodiments. In this example, themailing list messages are handled individually on a per recipient basis.When the summary of a quarantined mailing list message is sent to arecipient, the recipient can choose to unjunk the message. Accordingly,an unjunk request is sent to the message filter. Once the message filterreceives the unjunk request (500), the sender of the unjunk request isdetermined (502). In some embodiments, the unjunk request includes theaddress or other identifier of the sender who makes the request tofacilitate the determination. A copy of the message is then delivered tothe sender (504).

In some embodiments, the mailing list messages are handled for theentire group. When one of the mailing list's subscribers receives anotification about a quarantined mailing list message and unjunks themessage, the message is delivered to all the subscribers of the mailinglist. In some embodiments, a mailing list may have a delegate whoreviews the notification and makes unjunk decisions for all thesubscribers of the list.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive

1. (canceled)
 2. A method for sending notifications regardingdeclassification of suspicious messages, the method comprising:intercepting a suspicious message at a message filter, wherein themessage is addressed to a plurality of recipients; executinginstructions stored in memory, wherein execution of the instructions bya processor: identifies that the plurality of recipients include anindividual user and one or more mailing lists, determines that theindividual user is also subscribed to the one or more mailing lists, andgenerating a notification for each of the plurality of recipients,wherein a notification to the individual user is coalesced with anotification to the user as subscriber of the one or more mailing lists;and sending the coalesced notification to the user, wherein the userreceives only one notification regarding the suspicious message.